feat(wctt): RTA→WCTT release-jitter coupling (v0.9.2)#199
Merged
Conversation
avrabe
force-pushed
the
feat/v0.9.2-3-rta-wctt
branch
3 times, most recently
from
7f0a90c to
64934cf
Compare
Reviewer NC top-5 #4 — *single biggest credibility lift, no new math*. v0.8.x WCTT assumed the producing thread emits its burst "whenever"; the thread's response_time IS its release-jitter, which directly determines the burst at the NIC. When a stream's source end station declares `Timing_Properties::Dispatch_Jitter`, treat it as ingress release-jitter J and inflate the arrival burst σ by `ρ·J` bytes (ceiling-rounded so the bound is never under-estimated). New `WcttRtaCoupled` Info diagnostic per stream echoes the (jitter_ps, jitter_burst_bytes) pair so the coupling is visible. Default unset = 0 → byte-identical v0.8.1 / v0.9.1 output. The full automatic coupling — consume RTA's *computed* response_time directly without requiring the user to propagate via Dispatch_Jitter — is a v0.9.x follow-up; today the user must explicitly declare jitter (which is the canonical AS5506 property), but v0.9.2 wires the math so future automatic propagation is a one-line consumer change. REQ-NETWORK-011 + TEST-WCTT-RTA-COUPLING. 2 new tests (rta_wctt_dispatch_jitter_inflates_burst_and_emits_diagnostic, no_dispatch_jitter_no_coupling_diagnostic). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
avrabe
force-pushed
the
feat/v0.9.2-3-rta-wctt
branch
from
64934cf to
2299c18
Compare
avrabe
added a commit
that referenced
this pull request
May 3, 2026
Honesty + tightness pass. Closes 6 reviewer items + Lean spec align + org-wide CI concurrency control: - α(0)=0 causality fix (#193) — discharges 5/5 → 4 sorrys in MinPlus - Spar_TSN::Hi/Lo_Credit user-tunable CBS (#195) — Tier A #8 - WCTT sensitivity output (#196) — NC top-5 #13 - Stop_For_Lock + ARINC severity (#197) — Tier A #6 + #9 - Context_Switch in RTA recurrence (#198) — Tier A #5 (partial) - RTA→WCTT release-jitter coupling (#199) — NC top-5 #4 - Nightly fuzz + bench workflow fixes (#194) - Org-wide CI concurrency control (#200) Workspace version 0.9.1 → 0.9.2. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reviewer NC top-5 #4 — single biggest credibility lift. When source declares Dispatch_Jitter, inflate ingress burst by ρ·J. New WcttRtaCoupled Info diagnostic. Default unset = byte-identical.
Test plan: 2 new tests; workspace clean; clippy/fmt/rivet clean.
🤖 Generated with Claude Code